Bidirectional integration of information between a microblog and a data repository

ABSTRACT

Arrangements described herein relate to collaborative environments and, more particularly, to use of a microblog to enhance communication in an organization. The present arrangements can include receiving from a first user a first microblog entry into a microblog, identifying at least one keyword associated with the first microblog entry, and assigning to the at least one keyword a tag creating an association between the at least one keyword and at least one data repository. The arrangements further can include establishing bidirectional integration between the microblog and the at least one data repository of information related to the tag creating the association between the at least one keyword and the at least one data repository.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a Continuation of U.S. application Ser. No.14/251,357, filed on Apr. 11, 2014, the entirety of which isincorporated herein by reference.

BACKGROUND

Arrangements described herein relate to collaborative environments.

A collaborative environment is a computing environment supportingcollaboration among individuals. In a collaborative environment, peoplecan collaborate on projects and share information among each otherregardless of their respective geographic locations. For example, two ormore individuals can, in real-time, work together on documents,spreadsheets, drawings, etc., and share input to reach a common goal orunderstanding. In this regard, the use of collaborative environments inthe workplace can lead to increased productivity, especially on projectsrequiring input from many different individuals.

SUMMARY

A method includes receiving from a first user a first microblog entryinto a microblog, identifying at least one keyword associated with thefirst microblog entry, and assigning to the at least one keyword a tagcreating an association between the at least one keyword and at leastone data repository. The method further includes establishing, using aprocessor, bidirectional integration between the microblog and the atleast one data repository of information related to the tag creating theassociation between the at least one keyword and the at least one datarepository.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

FIG. 1 is a block diagram illustrating an example of a computingenvironment.

FIG. 2 is a block diagram illustrating example architecture for a dataprocessing system configured to host a microblog.

FIG. 3 is a flow chart illustrating an example of a method ofestablishing bidirectional integration of information between amicroblog and a data repository.

DETAILED DESCRIPTION

While the disclosure concludes with claims defining novel features, itis believed that the various features described herein will be betterunderstood from a consideration of the description in conjunction withthe drawings. The process(es), machine(s), manufacture(s) and anyvariations thereof described within this disclosure are provided forpurposes of illustration. Any specific structural and functional detailsdescribed are not to be interpreted as limiting, but merely as a basisfor the claims and as a representative basis for teaching one skilled inthe art to variously employ the features described in virtually anyappropriately detailed structure. Further, the terms and phrases usedwithin this disclosure are not intended to be limiting, but rather toprovide an understandable description of the features described.

This disclosure relates to collaborative environments and, moreparticularly, to use of a microblog to enhance communication in anorganization. In accordance with the inventive arrangements disclosedherein, users can generate microblog entries that are received by amicroblog. Keywords within the microblog entries can be identified andtags can be assigned to the keywords. The tags can create associationsbetween the keywords and relevant data repositories. Further,bidirectional integration of information related to the tags can beestablished between the microblog and the relevant data repositories.For example, the data repositories can be updated with information thatis contained in one or more microblog entries, and the microblog canpresent to users such information that is contained in the datarepository. In this regard, information entered by a user of themicroblog that is related to a particular subject can be automaticallyassociated with other information relevant to that subject and madereadily available to other users of the microblog. Accordingly, thearrangements described herein improve communication within anorganization, especially when team members are geographically dispersedamong different time zones.

Several definitions that apply throughout this document now will bepresented.

As used herein, the term “microblog” means a blog that receives fromusers, and publishes, informational updates. Posts in a microblogtypically are smaller both in actual and aggregated file size than postsin a traditional blog.

As used herein, the term “blog” means a web log that hosts a discussionand/or information and consisting of discrete entries (i.e., posts)published in a web based format.

As used herein, the term “micropost” means a microblog entry by a userinto a microblog.

As used herein, the term “keyword” means a word that serves as a meaningof another word, a sentence, a passage or the like.

As used herein, the term “tag” means a term assigned to a keyword thatcreates an association between the keyword and a relevant datarepository. For example, a tag may create an association between thekeyword and specific data contained in a relevant data repository. A tagmay be embodied as metadata.

As used herein, the term “data repository” means a central location(e.g., one or more databases) where data is stored and maintained.

As used herein, the term “bidirectional integration” means sharing ofdata between at least two entities in at least two directions.

As used herein, the term “real time” means a level of processingresponsiveness that a user or system senses as sufficiently immediatefor a particular process or determination to be made, or that enablesthe processor to keep up with some external process.

As defined herein, the term “processor” means at least one hardwarecircuit (e.g., an integrated circuit) configured to carry outinstructions contained in program code. Examples of a processor include,but are not limited to, a central processing unit (CPU), an arrayprocessor, a vector processor, a digital signal processor (DSP), afield-programmable gate array (FPGA), an application specific integratedcircuit (ASIC) and a controller.

As defined herein, the term “automatically” means without userintervention.

As defined herein, the term “user” means a person (i.e., a human being).

FIG. 1 is a block diagram illustrating an example of a computingenvironment 100. The computing environment can include a microblog 110,one or more client devices 120, 122, 124, 126 and one or more datarepositories 130, 132, 134, 136. The microblog 110 can be implemented assoftware and/or firmware executed on one or more processing systemscomprising at least one processor and memory, for example on one or moreservers. The client devices 120-126 each can be a processing systemcomprising at least one processor and memory, for example a workstation,desktop computer, mobile computer, laptop computer, notebook computer,tablet computer, smartphone, personal digital assistant, etc. Each datarepository 130-136 can comprise one or more data structures hosted onone or more computer readable storage mediums. Examples of datarepositories 130-136 include, but are not limited to, one or more datatables of one or more databases, hash tables, and the like. The datarepositories 130-136 can store, for example, information used by acollaboration environment, for example a collaborative lifecyclemanagement application. One example of a collaborative lifecyclemanagement application is IBM® Rational Team Concert™, though thepresent arrangements are not limited to this particular application.

The microblog 110, client devices 120-126 and data repositories 130-136can be communicatively linked via one or more communication networks.The communication network(s) is/are the medium used to providecommunications links between components 110, 120-126, 130-136 of thecomputing environment 100. The communication network(s) may includeconnections, such as wire, wireless communication links, or fiber opticcables. The communication network(s) can be implemented as, or include,any of a variety of different communication technologies such as a widearea network (WAN), a local area network (LAN), a wireless network, amobile network, a Virtual Private Network (VPN), the Internet, thePublic Switched Telephone Network (PSTN), or the like.

Via the communication network(s), users of the client devices 120-126can communicate microblog entries 140 to the microblog 110 using anysuitable form of communication. For example, the users of the clientdevices 120-126 can communicate microblog entries 140 (e.g., microposts)from the client devices 120-126 to the microblog 110 via emailcommunications, instant messaging, entries in one or more fields of awebpage/website, and the like. Similarly, the users of the clientdevices 120-126 can receive information from the microblog 110 on theclient devices 120-126 via email communications, instant messaging,presentation of one or more fields of a webpage/website, and the like.

In operation, a user of a client device 120 can communicate to themicroblog 110 a microblog entry 140 comprising text, one or more images,audio, video and/or multimedia. The microblog entry 140 can be amicropost to one or more microblog sections 112 of the microblog 110.For example, the microblog entry 140 can be a micropost to a sourcecontrol section of the microblog 110, a project management section ofthe microblog 110, a bug tracker section of the microblog 110, a problemmanagement record (PMR) section of the microblog 110, a Wiki and TeamCollaboration section of the microblog 110 and/or a StackOverflow andForums section of the microblog 110. It should be noted that these aremere examples of sections of a microblog 110 to which users may providemicroblog entries 140. Indeed, any of a variety of microblog sections112 may be provided to receive microblog entries 140 from users and thepresent arrangements are not limited in this regard.

The microblog 110 can include, or otherwise access, a microblog tool114. Responsive to receiving each microblog entry 140, the microblogtool 114 can review the microblog entry 140 to identify any content withwhich a keyword is associated. For example, the microblog tool 114 canidentify one or more keywords contained in text of the microblog entry140, identify one or more keywords contained in image, audio, videoand/or multimedia content contained in the microblog entry 140, identifyone or more keywords contained in objects referenced by the microblogentry 140, and the like. A microblog entry 140 may reference an object,such as a text, audio, image and/or multimedia file, by providing theobject as an attachment to the microblog entry 140 or providing a link,such as a uniform resource identifier (URI) (e.g., a uniform resourcelocator (URL)), to the object.

The microblog tool 114 can identify keywords by comparing theinformation contained in or referenced by the microblog entries 140 to adatabase of keywords. For example, the microblog tool 114 canautomatically parse each word contained in a microblog entry 140, oreach word contained in text referenced by the microblog entry 140, andcompare each word to the database of keywords. If a microblog entry 140contains or references an audio or multimedia file, the microblog tool114 can perform speech recognition on the audio or multimedia file toidentify individual words and compare each word to the database ofkeywords. If a microblog entry 140 contains or references an image ormultimedia file, the microblog tool 114 can identify words and/orobjects contained in the image or multimedia file to identify individualwords and/or objects and compare each word and/or word describing anidentified object to the database of keywords.

For each keyword that is identified, the microblog tool 114 canautomatically assign a tag 150 creating an association between thekeyword and a relevant data repository 130-136, and embed the tag in themicroblog entry 140. The tag 150 can be, for example, a hashtag, thoughthe present arrangements are not limited in this regard. Further, thetag 150 can be a link, or hyperlink, to relevant information containedin a data repository 130-136. In one aspect, a keyword identified in amicroblog entry 140 that is contained in text of the microblog entry 140can be converted into, or replaced with, a corresponding tag 150. In anarrangement in which a keyword is contained in content referenced by themicroblog entry 140, a tag 150 can be embedded in the microblog entry140 at a position near a location where the content is referenced, forexample above, below or beside such location. For example, if thecontent is referenced by a hyperlink, a tag 150 can be positioned nearthe hyperlink. If image, audio, video, and/or multimedia content isembedded in the microblog entry 140, a tag 150 can be positioned nearthe location of such content in the microblog entry 140, for exampleabove, below or beside such content.

By way of example, a user may generate a microblog entry 140 thatcontains the text “I fixed bug 5678 yesterday.” The microblog tool 114can identify the keywords “bug 5678” and assign the tag “bug 5678-n” tothe keywords, where n is an identifier that uniquely distinguishes thetag “bug 5678-n” from tags assigned to other microblog entries 140 thatreference the same bug. Further, the microblog tool can convert the text“bug 5678” into a hyperlink directed to information related to the bug5678 in a data repository of a defect tracking tool. For instance, thehyperlink can be configured to access relevant database recordspertaining to the bug 5678. When the hyperlink is selected by a user,the defect tracking tool can open with the relevant information beingdisplayed, or the relevant information can be presented to the user inthe microblog 110, for example via a user interface 116. In onearrangement, the user can modify and/or update the information, forexample to modify or update existing tasks, etc. Moreover, any updates(e.g., status updates, modifications, additions, etc.) to theinformation made by other users can be applied to the information beingpresented in real time. Accordingly, users always can be presented themost current information.

Accordingly, a user reviewing the microblog entry 140 can select the tag150 to access the relevant information 160, assuming the user isauthorized to access such data. In this regard, appropriate securitysettings can be implemented to allow users to view data they areauthorized to view and to prevent users from viewing data they are notauthorized to view. The microblog tool 114 can interface with anysuitable user account system, for example a system using the LightweightDirectory Access Protocol (LDAP) application protocol, to enforcesecurity settings contained in the user account system, identify users,etc.

The microblog tool 114 also can automatically process tags 150 assignedto keywords to update information in relevant data repositories 130-136with information 170 contained in the microblog entries 140 based on thetags 150. Continuing with the previous example, the word “fixed” in thesentence “I fixed bug 5678 yesterday” also can be identified as akeyword and a tag 150 can be assigned to that keyword. For example, thetag “corrected” can be assigned to the keyword “fixed.” The microblogtool 114 can process the tags “corrected” and “bug 5678-n” to update thedata repository of the defect tracking tool to indicate that the bug5678 has been corrected. For instance, the microblog tool 114 caninterface with the defect tracking tool to update one or more databaserecords related to the bug 5678 in real time.

Further, the microblog tool 114 can store the microblog entries 140 andtags 150 to one or more relevant data repositories 130-136 not only topersist the data, but also to enable information searches using the tags150. For example, via the user interface 116, users can interface withthe microblog tool 114 to search for microblog entries pertaining to aparticular subject and/or search the data repositories 130-136 forinformation pertaining to the subject. Thus, even if original messagesfor microblog entries are lost, the information contained in themicroblog entries will be retained. Moreover, from the microblog 110,the user can search and access information not contained in themicroblog entries 140, for example information used by a collaborativelifecycle management application. Also, via the user interface 116,users can enter updates (e.g., status updates, modifications, additions,etc.) to the information. As noted, updates to the information can bepropagated in real time so that other users viewing the same informationwill be presented the updates/essentially when they occur.

Via the user interface 116, the microblog tool 114 can provide a numberof different information filters, selectable by the user, to facilitatethe information searches. For example, a global filter can be providedto allow a user to view information provided by anyone in microblogentries 140 and/or by updates made to the data repositories 130-136. Auser filter can be provided to allow a user to view such informationprovided by a particular person. A personal (or group) filter can beprovided to allow a user to view such information provided by particularpeople and/or people located in a particular geographic location. A tagfilter can be provided to allow a user to view such informationassociated with a particular tag. A recommended filter can be providedto allow a user to view information relevant to a project or task theuser presently is working on or related to information previouslyprovided by the user. In this regard, the microblog tool 114 can analyzeinformation entered into the microblog 110 by the user and/orinformation accessed by the user using the microblog 110 to identify therelated information. A time filter can be provided to allow a user toview information provided at a particular time, provided in a particulartime frame and/or provided by users located in a particular time zone.Also, the microblog tool 114 can provide, via the user interface 116,various options/menus that allow users to create custom filters tofilter information based on specific criteria. Still, any number ofother filters can be provided and the present arrangements are notlimited in this regard.

The filters described herein can be implemented using suitable queries,for example queries configured in accordance with structured querylanguage (SQL). Use of the filters can facilitate not only access toinformation contained in microblog entries 140 and other informationcontained in the data repositories 130-136, but also facilitate analysisof such information. In this regard, users can selectively filter theinformation being accessed based on a particular context (e.g., time,time zone, geographic location, project, team, etc.), thus providinghighly efficient access to desired information.

FIG. 2 is a block diagram illustrating example architecture for a dataprocessing system 200 configured to host the microblog 110 of FIG. 1.The processing system 200 can include at least one processor 205 (e.g.,a central processing unit) coupled to memory elements 210 through asystem bus 215 or other suitable circuitry. As such, the processingsystem 200 can store program code within the memory elements 210. Theprocessor 205 can execute the program code accessed from the memoryelements 210 via the system bus 215. It should be appreciated that theprocessing system 200 can be implemented in the form of any systemincluding a processor and memory that is capable of performing thefunctions and/or operations described within this specification.

The memory elements 210 can include one or more physical memory devicessuch as, for example, local memory 220 and one or more bulk storagedevices 225. Local memory 220 refers to random access memory (RAM) orother non-persistent memory device(s) generally used during actualexecution of the program code. The bulk storage device(s) 225 can beimplemented as a hard disk drive (HDD), solid state drive (SSD), orother persistent data storage device. The processing system 200 also caninclude one or more cache memories (not shown) that provide temporarystorage of at least some program code in order to reduce the number oftimes program code must be retrieved from the bulk storage device 225during execution.

One or more network adapters 230 also can be coupled to processingsystem 200 to enable processing system 200 to become coupled to othersystems, computer systems, remote data storage devices and/or remoteprinters through intervening private or public networks. Modems, cablemodems, transceivers, and Ethernet cards are examples of different typesof network adapters 230 that can be used with the processing system 200.

As pictured in FIG. 2, the memory elements 210 can store the microblog110, including the microblog sections 112, the microblog tool 114, theuser interface 116 and the tags 150. The microblog 110 and microblogtool 114, being implemented in the form of executable program code, areexecuted by the data processing system 200 and, as such, are consideredintegrated parts of the data processing system 200. Moreover, themicroblog 110, microblog sections 112, microblog tool 114, userinterface 116 and tags 150, including any parameters and/or attributesutilized by these components, are functional data structures that impartfunctionality when employed as part of data processing system 200.

FIG. 3 is a flow chart illustrating an example of a method 300 ofestablishing bidirectional integration of information between amicroblog and a data repository. At step 302, a first microblog entryinto a microblog can be received from a first user. At step 304, atleast one keyword associated with the first microblog entry can beidentified. At step 306, a tag creating an association between the atleast one keyword and at least one data repository can be assigned tothe at least one keyword. At step 308, bidirectional integration betweenthe microblog and the at least one data repository of informationrelated to the tag creating the association between the at least onekeyword and the at least one data repository can be established using aprocessor.

For purposes of simplicity and clarity of illustration, elements shownin the figures have not necessarily been drawn to scale. For example,the dimensions of some of the elements may be exaggerated relative toother elements for clarity. Further, where considered appropriate,reference numbers are repeated among the figures to indicatecorresponding, analogous, or like features.

The present invention may be a system, a method, and/or a computerprogram product. The computer program product may include a computerreadable storage medium (or media) having computer readable programinstructions thereon for causing a processor to carry out aspects of thepresent invention.

The computer readable storage medium can be a tangible device that canretain and store instructions for use by an instruction executiondevice. The computer readable storage medium may be, for example, but isnot limited to, an electronic storage device, a magnetic storage device,an optical storage device, an electromagnetic storage device, asemiconductor storage device, or any suitable combination of theforegoing. A non-exhaustive list of more specific examples of thecomputer readable storage medium includes the following: a portablecomputer diskette, a hard disk, a random access memory (RAM), aread-only memory (ROM), an erasable programmable read-only memory (EPROMor Flash memory), a static random access memory (SRAM), a portablecompact disc read-only memory (CD-ROM), a digital versatile disk (DVD),a memory stick, a floppy disk, a mechanically encoded device such aspunch-cards or raised structures in a groove having instructionsrecorded thereon, and any suitable combination of the foregoing. Acomputer readable storage medium, as used herein, is not to be construedas being transitory signals per se, such as radio waves or other freelypropagating electromagnetic waves, electromagnetic waves propagatingthrough a waveguide or other transmission media (e.g., light pulsespassing through a fiber-optic cable), or electrical signals transmittedthrough a wire.

Computer readable program instructions described herein can bedownloaded to respective computing/processing devices from a computerreadable storage medium or to an external computer or external storagedevice via a network, for example, the Internet, a local area network, awide area network and/or a wireless network. The network may comprisecopper transmission cables, optical transmission fibers, wirelesstransmission, routers, firewalls, switches, gateway computers and/oredge servers. A network adapter card or network interface in eachcomputing/processing device receives computer readable programinstructions from the network and forwards the computer readable programinstructions for storage in a computer readable storage medium withinthe respective computing/processing device.

Computer readable program instructions for carrying out operations ofthe present invention may be assembler instructions,instruction-set-architecture (ISA) instructions, machine instructions,machine dependent instructions, microcode, firmware instructions,state-setting data, or either source code or object code written in anycombination of one or more programming languages, including an objectoriented programming language such as Smalltalk, C++ or the like, andconventional procedural programming languages, such as the “C”programming language or similar programming languages. The computerreadable program instructions may execute entirely on the user'scomputer, partly on the user's computer, as a stand-alone softwarepackage, partly on the user's computer and partly on a remote computeror entirely on the remote computer or server. In the latter scenario,the remote computer may be connected to the user's computer through anytype of network, including a local area network (LAN) or a wide areanetwork (WAN), or the connection may be made to an external computer(for example, through the Internet using an Internet Service Provider).In some embodiments, electronic circuitry including, for example,programmable logic circuitry, field-programmable gate arrays (FPGA), orprogrammable logic arrays (PLA) may execute the computer readableprogram instructions by utilizing state information of the computerreadable program instructions to personalize the electronic circuitry,in order to perform aspects of the present invention.

Aspects of the present invention are described herein with reference toflowchart illustrations and/or block diagrams of methods, apparatus(systems), and computer program products according to embodiments of theinvention. It will be understood that each block of the flowchartillustrations and/or block diagrams, and combinations of blocks in theflowchart illustrations and/or block diagrams, can be implemented bycomputer readable program instructions.

These computer readable program instructions may be provided to aprocessor of a general purpose computer, special purpose computer, orother programmable data processing apparatus to produce a machine, suchthat the instructions, which execute via the processor of the computeror other programmable data processing apparatus, create means forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks. These computer readable program instructionsmay also be stored in a computer readable storage medium that can directa computer, a programmable data processing apparatus, and/or otherdevices to function in a particular manner, such that the computerreadable storage medium having instructions stored therein comprises anarticle of manufacture including instructions which implement aspects ofthe function/act specified in the flowchart and/or block diagram blockor blocks.

The computer readable program instructions may also be loaded onto acomputer, other programmable data processing apparatus, or other deviceto cause a series of operational steps to be performed on the computer,other programmable apparatus or other device to produce a computerimplemented process, such that the instructions which execute on thecomputer, other programmable apparatus, or other device implement thefunctions/acts specified in the flowchart and/or block diagram block orblocks.

The flowchart and block diagrams in the Figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods, and computer program products according to variousembodiments of the present invention. In this regard, each block in theflowchart or block diagrams may represent a module, segment, or portionof instructions, which comprises one or more executable instructions forimplementing the specified logical function(s). In some alternativeimplementations, the functions noted in the block may occur out of theorder noted in the figures. For example, two blocks shown in successionmay, in fact, be executed substantially concurrently, or the blocks maysometimes be executed in the reverse order, depending upon thefunctionality involved. It will also be noted that each block of theblock diagrams and/or flowchart illustration, and combinations of blocksin the block diagrams and/or flowchart illustration, can be implementedby special purpose hardware-based systems that perform the specifiedfunctions or acts or carry out combinations of special purpose hardwareand computer instructions.

The terminology used herein is for the purpose of describing particularembodiments only and is not intended to be limiting of the invention. Asused herein, the singular forms “a,” “an,” and “the” are intended toinclude the plural forms as well, unless the context clearly indicatesotherwise. It will be further understood that the terms “includes,”“including,” “comprises,” and/or “comprising,” when used in thisdisclosure, specify the presence of stated features, integers, steps,operations, elements, and/or components, but do not preclude thepresence or addition of one or more other features, integers, steps,operations, elements, components, and/or groups thereof.

Reference throughout this disclosure to “one embodiment,” “anembodiment,” or similar language means that a particular feature,structure, or characteristic described in connection with the embodimentis included in at least one embodiment described within this disclosure.Thus, appearances of the phrases “in one embodiment,” “in anembodiment,” and similar language throughout this disclosure may, but donot necessarily, all refer to the same embodiment.

The term “plurality,” as used herein, is defined as two or more thantwo. The term “another,” as used herein, is defined as at least a secondor more. The term “coupled,” as used herein, is defined as connected,whether directly without any intervening elements or indirectly with oneor more intervening elements, unless otherwise indicated. Two elementsalso can be coupled mechanically, electrically, or communicativelylinked through a communication channel, pathway, network, or system. Theterm “and/or” as used herein refers to and encompasses any and allpossible combinations of one or more of the associated listed items. Itwill also be understood that, although the terms first, second, etc. maybe used herein to describe various elements, these elements should notbe limited by these terms, as these terms are only used to distinguishone element from another unless stated otherwise or the contextindicates otherwise.

The term “if” may be construed to mean “when” or “upon” or “in responseto determining” or “in response to detecting,” depending on the context.Similarly, the phrase “if it is determined” or “if [a stated conditionor event] is detected” may be construed to mean “upon determining” or“in response to determining” or “upon detecting [the stated condition orevent]” or “in response to detecting [the stated condition or event],”depending on the context.

The descriptions of the various embodiments of the present inventionhave been presented for purposes of illustration, but are not intendedto be exhaustive or limited to the embodiments disclosed. Manymodifications and variations will be apparent to those of ordinary skillin the art without departing from the scope and spirit of the describedembodiments. The terminology used herein was chosen to best explain theprinciples of the embodiments, the practical application or technicalimprovement over technologies found in the marketplace, or to enableothers of ordinary skill in the art to understand the embodimentsdisclosed herein.

What is claimed is:
 1. A method, comprising: receiving from a first usera first microblog entry into a microblog; identifying at least onekeyword associated with the first microblog entry; assigning to the atleast one keyword a tag creating an association between the at least onekeyword and at least one data repository, the tag comprising anidentifier that uniquely distinguishes the tag from at least one othertag assigned to the at least one keyword for at least a second microblogentry; storing, to the at least one data repository, information relatedto the tag creating the association between the at least one keyword andthe at least one data repository; converting the at least one keywordassociated with the first microblog entry to a hyperlink directed to theinformation related to the tag at the at least one data repository;establishing, using a processor, bidirectional integration between themicroblog and the at least one data repository of the informationrelated to the tag creating the association between the at least onekeyword and the at least one data repository, wherein the bidirectionalintegration between the microblog and the at least one data repositoryenables sharing between the microblog and the at least one datarepository, in at least two directions, of the information related tothe tag creating the association between the at least one keyword andthe at least one data repository; and responsive to a second userselecting the hyperlink, presenting to the second user a plurality ofdatabase records, from the at least one data repository, pertaining tothe keyword in the microblog.
 2. The method of claim 1, furthercomprising: responsive to receiving the first microblog entry into themicroblog, based on the tag, updating information in the at least onedata repository with information contained in the first microblog entry.3. The method of claim 2, wherein the information in the at least onedata repository is not the first microblog entry or the second microblogentry.
 4. The method of claim 2, further comprising: presenting, in realtime, the updated information in the at least one data repository to thesecond user viewing the information in the at least one data repositoryvia the microblog.
 5. The method of claim 1, further comprising:receiving from the first user or the second user a selection of the tagvia the microblog; and responsive to receiving the selection of the tag,presenting to the first user or the second user, via the microblog, theinformation related to the tag.
 6. The method of claim 1, furthercomprising: receiving from the first user or the second user, via themicroblog, a selection of at least one information filter; filtering,using the at least one information filter, the information which is usedby the at least one data repository; and presenting to the first user orthe second user, via the microblog, the filtered information used by theat least one data repository.
 7. The method of claim 1, furthercomprising: identifying at least a second keyword associated with thefirst microblog entry; assigning to the second keyword a second tagcreating an association between the second keyword and the at least onedata repository; and updating at least one record in the at least onedata repository by processing the first tag and the second tag.
 8. Themethod of claim 7, wherein: the at least one keyword is a keyword usedby a collaborative lifecycle management application; the second keywordidentifies an action corresponding to the keyword used by thecollaborative lifecycle management application; the record in the atleast one data repository identifies the keyword used by thecollaborative lifecycle management application; and updating the atleast one record in the at least one data repository comprises updatingthe record to indicate the action corresponding to the keyword used bythe collaborative lifecycle management application.
 9. The method ofclaim 1, further comprising: receiving from the second user at least oneuser input specifying a modification or update to at least one of theplurality of database records pertaining to the keyword; and applying,in real time, the modification or update to the at least one of theplurality of database records; wherein, the modification or update tothe at least one of the plurality of database records is propagated, inreal time, to a view of the microblog presented to the first user or atleast a third user.